FHIR © HL7.org  |  Server Home  |  FHIR Server FHIR Server 3.4.11  |  FHIR Version n/a  User: [n/a]

Resource ValueSet/FHIR Server from package hl7.terminology#current (47 ms)

Package hl7.terminology
Type ValueSet
Id Id
FHIR Version R5
Source http://terminology.hl7.org/https://build.fhir.org/ig/HL7/UTG/ValueSet-v3-ActRelationshipDocumentHQMF.html
Url http://terminology.hl7.org/ValueSet/v3-ActRelationshipDocumentHQMF
Version 3.0.0
Status active
Date 2014-08-07
Name ActRelationshipDocumentHQMF
Title ActRelationshipDocumentHQMF
Experimental False
Realm uv
Authority hl7
Description The reasons that may be used when relating a Quality Measure Document to other document types.
Copyright This material derives from the HL7 Terminology THO. THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html

Resources that use this resource

No resources found


Resources that this resource uses

CodeSystem
v3-ActRelationshipType ActRelationshipType


Narrative

Note: links and images are rebased to the (stated) source

Generated Narrative: ValueSet v3-ActRelationshipDocumentHQMF

Language: en

  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType
    CodeDisplayDefinition
    COMPhas componentThe target act is a component of the source act, with no semantics regarding composition or aggregation implied.
    DRIVis derived fromAssociates a derived Act with its input parameters. E.G., an anion-gap observation can be associated as being derived from given sodium-, (potassium-,), chloride-, and bicarbonate-observations. The narrative content (Act.text) of a source act is wholly machine-derived from the collection of target acts.
    RPLCreplacesA replacement source act replaces an existing target act. The state of the target act being replaced becomes obselete, but the act is typically still retained in the system for historical reference. The source and target must be of the same type.
    USEusesIndicates that the source act makes use of (or will make use of) the information content of the target act.

    *UsageNotes:* A usage relationship only makes sense if the target act is authored and occurs independently of the source act. Otherwise a simpler relationship such as COMP would be appropriate.

    *Rationale:* There is a need when defining a clinical trial protocol to indicate that the protocol makes use of other protocol or treatment specifications. This is stronger than the assertion of "references". References may exist without usage, and in a clinical trial protocol is common to assert both: what other specifications does this trial use and what other specifications does it merely reference.
    XCRPTExcerptsThe source is an excerpt from the target.
    XFRMtransformationUsed when the target Act is a transformation of the source Act. (For instance, used to show that a CDA document is a transformation of a DICOM SR document.)

Source

{
  "resourceType" : "ValueSet",
  "id" : "v3-ActRelationshipDocumentHQMF",
  "language" : "en",
  "text" : {
    "status" : "extensions",
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\" xml:lang=\"en\" lang=\"en\"><p class=\"res-header-id\"><b>Generated Narrative: ValueSet v3-ActRelationshipDocumentHQMF</b></p><a name=\"v3-ActRelationshipDocumentHQMF\"> </a><a name=\"hcv3-ActRelationshipDocumentHQMF\"> </a><a name=\"v3-ActRelationshipDocumentHQMF-en-US\"> </a><div style=\"display: inline-block; background-color: #d9e0e7; padding: 6px; margin: 4px; border: 1px solid #8da1b4; border-radius: 5px; line-height: 60%\"><p style=\"margin-bottom: 0px\">Language: en</p></div><ul><li>Include these codes as defined in <a href=\"CodeSystem-v3-ActRelationshipType.html\"><code>http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType</code></a><table class=\"none\"><tr><td style=\"white-space:nowrap\"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td></tr><tr><td><a href=\"CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-COMP\">COMP</a></td><td style=\"color: #cccccc\">has component</td><td>The target act is a component of the source act, with no semantics regarding composition or aggregation implied.</td></tr><tr><td><a href=\"CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-DRIV\">DRIV</a></td><td style=\"color: #cccccc\">is derived from</td><td>Associates a derived Act with its input parameters. E.G., an anion-gap observation can be associated as being derived from given sodium-, (potassium-,), chloride-, and bicarbonate-observations. The narrative content (Act.text) of a source act is wholly machine-derived from the collection of target acts.</td></tr><tr><td><a href=\"CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-RPLC\">RPLC</a></td><td style=\"color: #cccccc\">replaces</td><td>A replacement source act replaces an existing target act. The state of the target act being replaced becomes obselete, but the act is typically still retained in the system for historical reference. The source and target must be of the same type.</td></tr><tr><td><a href=\"CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-USE\">USE</a></td><td style=\"color: #cccccc\">uses</td><td>Indicates that the source act makes use of (or will make use of) the information content of the target act.<br/><br/>*UsageNotes:* A usage relationship only makes sense if the target act is authored and occurs independently of the source act. Otherwise a simpler relationship such as COMP would be appropriate.<br/><br/>*Rationale:* There is a need when defining a clinical trial protocol to indicate that the protocol makes use of other protocol or treatment specifications. This is stronger than the assertion of &quot;references&quot;. References may exist without usage, and in a clinical trial protocol is common to assert both: what other specifications does this trial use and what other specifications does it merely reference.</td></tr><tr><td><a href=\"CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-XCRPT\">XCRPT</a></td><td style=\"color: #cccccc\">Excerpts</td><td>The source is an excerpt from the target.</td></tr><tr><td><a href=\"CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-XFRM\">XFRM</a></td><td style=\"color: #cccccc\">transformation</td><td>Used when the target Act is a transformation of the source Act. (For instance, used to show that a CDA document is a transformation of a DICOM SR document.)</td></tr></table></li></ul></div>"
  },
  "url" : "http://terminology.hl7.org/ValueSet/v3-ActRelationshipDocumentHQMF",
  "identifier" : [
    {
      "system" : "urn:ietf:rfc:3986",
      "value" : "urn:oid:2.16.840.1.113883.1.11.20522"
    }
  ],
  "version" : "3.0.0",
  "name" : "ActRelationshipDocumentHQMF",
  "title" : "ActRelationshipDocumentHQMF",
  "status" : "active",
  "experimental" : false,
  "date" : "2014-08-07",
  "publisher" : "Health Level Seven International",
  "contact" : [
    {
      "telecom" : [
        {
          "system" : "url",
          "value" : "http://hl7.org"
        },
        {
          "system" : "email",
          "value" : "hq@HL7.org"
        }
      ]
    }
  ],
  "description" : "The reasons that may be used when relating a Quality Measure Document to other document types.",
  "immutable" : true,
  "copyright" : "This material derives from the HL7 Terminology THO. THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html",
  "compose" : {
    "include" : [
      {
        "system" : "http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType",
        "concept" : [
          {
            "code" : "COMP"
          },
          {
            "code" : "DRIV"
          },
          {
            "code" : "RPLC"
          },
          {
            "code" : "USE"
          },
          {
            "code" : "XCRPT"
          },
          {
            "code" : "XFRM"
          }
        ]
      }
    ]
  }
}

XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.